-
Notifications
You must be signed in to change notification settings - Fork 121
Fix reflective BC for stresses #814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@sbryngelson Do you know what's causing this error? It works locally and I haven't seen this before. I also didn't change any compilation settings or FFTW-related stuff. Thanks! |
|
Try recompiling/re-running the runners. it could be that the run got killed by something. another possibility is that FFTW ended up with a bug in a new release or something, but this seems less likely. |
|
If only Ubuntu runners are failing, I wonder if something went wrong with a new FFTW version grabbed by those Ubuntu runs. Looking at the workflow file, we have - name: Setup Ubuntu
if: matrix.os == 'ubuntu' && matrix.intel == false
run: |
sudo apt update -y
sudo apt install -y cmake gcc g++ python3 python3-dev hdf5-tools \
libfftw3-dev libhdf5-dev openmpi-bin libopenmpi-devYou could look at a previous PR to see if the version has changed in the last day or so. If MacOS is also failing then it is probably a different problem because we |
|
@sbryngelson Thank you very much for the tips! I've tried a few things and will discuss on Slack. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #814 +/- ##
==========================================
+ Coverage 43.42% 43.54% +0.12%
==========================================
Files 66 66
Lines 19699 19725 +26
Branches 2402 2405 +3
==========================================
+ Hits 8554 8590 +36
+ Misses 9673 9660 -13
- Partials 1472 1475 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Description
Fixes symmetric boundary (
bc=-2) conditions for stresses (elasticity simulations).Type of change
Scope
How Has This Been Tested?
output.mp4
output.mp4
Checklist
docs/)examples/that demonstrate my new feature performing as expected.They run to completion and demonstrate "interesting physics"
./mfc.sh formatbefore committing my codeIf your code changes any code source files (anything in
src/simulation)To make sure the code is performing as expected on GPU devices, I have:
nvtxranges so that they can be identified in profiles./mfc.sh run XXXX --gpu -t simulation --nsys, and have attached the output file (.nsys-rep) and plain text results to this PR./mfc.sh run XXXX --gpu -t simulation --omniperf, and have attached the output file and plain text results to this PR.